Ensure correct OpenID Connect error responses #16982
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites
Description
This PR aligns the custom error responses from the auth parts of the Management and Delivery APIs with those of OpenIddict, which in turn are aligned with the OpenID Connect standard.
Testing this PR
Invalid auth requests should have responses that conform to the standard.
For example attempting to use an invalid
client_id
(this is a custom error response inMemberController
):....compared to using an invalid
redirect_uri
(this is a response from OpenIddict):